翻訳と辞書
Words near each other
・ Servian constitution
・ Servian Wall
・ Servian, Hérault
・ Service
・ Service & Food Workers Union
・ Service (album)
・ Service (economics)
・ Service (film)
・ Service (motor vehicle)
・ Service (music)
・ Service (play)
・ Service (record label)
・ Service (surname)
・ Service (systems architecture)
・ Service 4.0
Service abstraction
・ Service Access Point
・ Service action network
・ Service address
・ Service Advertising Protocol
・ Service and Reform List
・ Service animal
・ Service area
・ Service as a product
・ Service assurance
・ Service Assurance Agent
・ Service autonomy principle
・ Service Availability Forum
・ Service award
・ Service Award Cross


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Service abstraction : ウィキペディア英語版
Service abstraction

Service abstraction is a design principle that is applied within the service-orientation design paradigm so that the information published in a service contract is limited to what is required to effectively utilize the service〔(Service )〕 The service contract should not contain any superfluous information that is not required for its invocation. Also that the information should be limited to the serviced contract (technical contract and the SLA) only, no other document or medium should be made available to the service consumers other than the service contract that contains additional service related information.
==Purpose==
A service contract that contains details about what is encapsulates e.g. the logic, implementation and the technology used to build the service, may end up being used in a particular manner as now the service consumer has more knowledge about the working of the service. Under normal circumstances, the more knowledge we have, the better it is but in case of service-orientation, there is a chance that the additional information could impede the reusability of the service as the service consumer designer may streamline his design based on this knowledge, however, this would affect the evolution of the service contract as now the service consumer is indirectly coupled to the service implementation, which may need to be replaced in the future. In a way, this increases the consumer-to-contract type of coupling, which although is a positive type of coupling but having too much dependence can negatively impact the evolution of both the service provider and the service consumer.
Information hiding remains one of the key principles within object-oriented paradigm that promotes abstracting away the inner workings of a software program. A classic example would be the use of abstract classes to hide the actual method logic. The same concept is applied by the service abstraction principle in order to hide the unnecessary details about the working of the service with a view to ease the evolution of the service.〔Dennis Wisnosky.(Principles and Patterns at the U.S. Department of Defense )().Date accessed: 13 April 2010.〕

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Service abstraction」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.